@DTEAM HW renderer functionality should be online with latest git commit. It looks like there is a significant performance uplift at least on the Pi4. That said, I recommend not turning on shader cache in Borked3DS as it seems like the shaders are already getting cached in a whole bunch of places and turning it on just makes things even slower when they are first being compiled and cached. The game will actually seemingly crash a bunch of times (or just have a very long pause) when you first turn hardware shader acceleration on as shaders are getting compiled for the first time, that said after a while gameplay should become pretty smooth and noticeably better than with hardware shader acceleration turned off.

Note that if for some reason you need to delete your shader cache, it is a bit of a pain on the Pi as the shaders are cached not just in the location that Borked3DS deletes from within the gui. The solution I found was that I had to manually delete all locations of the shader cache in borked as well as all locations of the mesa shader cache:

sudo rm -r /home/pi/.local/share/borked3ds-emu/shaders/ mv /home/pi/.cache/mesa_shader_cache /home/pi/.cache/mesa_shader_cache_bad mv /home/pi/.cache/mesa_shader_cache_db/ /home/pi/.cache/mesa_shader_cache_db_bad sudo su sudo rm -r /root/.local/share/borked3ds-emu/shaders/ sudo rm -r /root/.local/share/borked3ds-emu/borked3ds-emu/shaders/ sudo mv /root/.cache/mesa_shader_cache /root/.cache/mesa_shader_cache_bad sudo mv /root/.cache/mesa_shader_cache_db/ /root/.cache/mesa_shader_cache_db_bad

Note that you can delete those bad mesa shader directories once you are sure that the removal doesn't cause unforeseen issues on your Pi.